Skip to content

ci: upgrade GitHub Actions to Node.js 24-compatible versions#10

Merged
mroman-recurly merged 3 commits into
masterfrom
jparrabedoya/SWI-5336
Jun 3, 2026
Merged

ci: upgrade GitHub Actions to Node.js 24-compatible versions#10
mroman-recurly merged 3 commits into
masterfrom
jparrabedoya/SWI-5336

Conversation

@jparrabedoya

Copy link
Copy Markdown
Contributor

Description

Problem

GitHub Actions is deprecating Node.js 20. Actions using Node.js 20 will be forced to run on Node.js 24 starting June 2026, and Node.js 20 will be fully removed from runners in September 2026. The actions/checkout@v3 action used in the ESLint workflow runs on node16, which is also affected.

See: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Fix

Upgraded actions/checkout from v3 (node16) to v6.0.3 (node24) in the ESLint security check workflow.

The stefanoeb/eslint-action@1.0.2 action uses a Docker runtime and is not affected by this deprecation.

Files Changed

  • .github/workflows/eslint.yml — upgraded actions/checkout from v3 to v6.0.3; added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true env flag for CI validation (to be removed before merge)

Testing

CI runs on this PR with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true to verify all JavaScript actions run under Node.js 24. The flag will be removed in a follow-up commit before merge.

jparrabedoya and others added 2 commits June 3, 2026 15:08
Upgrade actions/checkout from v3 (node16) to v6.0.3 (node24) in
eslint.yml to remediate the GitHub Actions Node.js 20 deprecation.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Temporary flag to force Node.js 24 runtime during CI validation.
Will be removed before merge.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@jparrabedoya jparrabedoya self-assigned this Jun 3, 2026
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@mroman-recurly mroman-recurly merged commit 7eaec03 into master Jun 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants